Cross-Border Legal Mistakes Startups Make (Canada–US)
I am licensed in both Ontario and New York. I've watched the same mistakes happen from both sides of the border, and they're almost always the same mistakes.
Not because founders are careless. Because the Canada–US legal landscape looks simpler than it is, and the gaps don't show up until something goes wrong.
Here are the ones I see most often.
Mistake 1: Assuming one jurisdiction covers the other
This is the foundational error. A Canadian founder incorporates federally or provincially, gets their articles, and assumes they're set up to do business in the U.S. They're not.
Doing business in the United States — actually doing business, with contracts, employees, customers, and revenue — creates legal presence in U.S. jurisdictions. That presence comes with registration requirements, tax obligations, and regulatory exposure that the Canadian entity does not automatically satisfy.
The reverse is also true. A Delaware C-corp with Canadian employees and Canadian customers may have significant exposure under Canadian law — employment standards, privacy legislation, tax nexus — that the U.S. structure doesn't address.
The fix: When you're operating in both countries, you usually need legal structure in both countries. What that looks like depends on your business model, your revenue streams, and where your people are. It is not one-size-fits-all. But the starting assumption — that one entity covers everything — is almost always wrong.
Mistake 2: Using the wrong employment model
Employment law is not the same on both sides of the border. Not even close.
Termination: In Canada — and especially in Ontario — common law notice requirements for termination without cause are substantially more generous than most founders expect. A five-year employee in Ontario may be entitled to five to nine months of reasonable notice, regardless of what the employment contract says. Many U.S.-founded startups operating in Canada discover this when they try to terminate someone and find out their U.S. "at will" expectations do not apply.
Classification: The contractor vs. employee distinction is strictly enforced in Canada and in most U.S. states. Misclassifying an employee as an independent contractor creates significant exposure: back taxes, employment standards liability, CPP/EI contributions in Canada, FICA in the U.S. The fact that someone signed a contract calling themselves a contractor does not make them one.
Benefits and leave: Minimum entitlements for statutory holidays, parental leave, and sick leave vary significantly between Canadian provinces and U.S. states. Ontario has some of the most employee-protective legislation in North America. Founders used to operating in right-to-work U.S. states are often surprised.
The fix: Before you hire anyone in a new jurisdiction — Canadian or American — understand the employment law in that jurisdiction. Don't import your existing employment agreement. Don't assume the rules are similar. They're not.
Mistake 3: Privacy law assumptions running in the wrong direction
U.S. founders expanding to Canada often underestimate PIPEDA (soon to be replaced by Bill C-27 under the Consumer Privacy Protection Act). Canadian privacy law is more stringent than U.S. federal privacy law in several meaningful ways, including consent requirements for data collection, use limitations, and cross-border data transfer obligations.
Canadian founders expanding to the U.S. often underestimate the state-level patchwork. California's CPRA is the most comprehensive, but Virginia, Colorado, Connecticut, and a growing number of states have their own frameworks. If you have customers in multiple U.S. states, you may be subject to multiple overlapping regimes.
Both make assumptions based on what they know. Both are wrong.
The fix: Privacy compliance is not a "we'll deal with it later" item. It's a structural question that affects how you collect data, where you store it, what you disclose, and what rights your users have. Get a privacy audit before you expand, not after a regulator asks why you didn't.
Mistake 4: IP ownership that doesn't travel
Intellectual property assignments need to be effective in every jurisdiction where the IP might be contested. A Canadian assignment that's perfectly valid under Ontario law may not be enforceable in a U.S. court without additional steps. A U.S. work-for-hire clause that functions automatically under U.S. copyright law does not function the same way in Canada, where moral rights exist and cannot be assigned.
The IP issues I see most often in cross-border companies:
Founder IP assignment agreements that were drafted for one jurisdiction and don't work in the other
Contractor agreements with U.S. contractors that don't include adequate IP assignment (because it seemed obvious)
Open-source licence obligations that nobody tracked through an acquisition
Trade secret protection that depends on reasonable measures that weren't taken
None of these are fatal on their own. All of them become problems in a due diligence process, an acquisition, or a licensing dispute.
The fix: If your IP is core to your business — and for most startups it is — have it reviewed by someone who understands both jurisdictions. The assignment needs to work everywhere you operate.
Mistake 5: Investor documentation that doesn't account for cross-border compliance
This one is technical but important. Canadian companies raising capital from U.S. investors — or U.S. companies raising from Canadian investors — trigger securities law requirements in multiple jurisdictions simultaneously.
In Canada, National Instrument 45-106 governs exempt market offerings. The accredited investor exemption exists, but the thresholds and definitions are not identical to the U.S. equivalent under Regulation D. The offering memorandum exemption has additional disclosure requirements. The minimum amount exemption has conditions. None of these are obvious from a U.S.-centric cap table perspective.
In the U.S., Form D filings are often missed or filed late by Canadian issuers who didn't know they needed them. State blue sky laws add another layer that's easy to miss when you're thinking about federal compliance.
The result: a financing that was properly papered on one side of the border, partially papered on the other, and creates cleanup costs or liability that the company didn't anticipate.
The fix: If you're raising from investors across the border — either direction — use counsel who is admitted in both jurisdictions or who has working relationships with counsel on both sides. The documentation needs to satisfy both regulatory regimes, and "we used our U.S. lawyers" or "we used our Canadian lawyers" is not sufficient for the other side.
Mistake 6: Treating a cross-border acquisition like a domestic one
Acquisitions involving Canadian and U.S. entities — either as acquirer or target — create a due diligence process that's twice as long as either side expects, and a closing process that requires coordination across legal systems, tax regimes, and regulatory frameworks that don't always talk to each other cleanly.
Common issues:
Canadian asset or share sale structures that don't translate to U.S. tax treatment the acquirer wanted
Section 116 Canadian tax withholding requirements that aren't caught until late in the process and require Canadian Revenue Agency certificates that take time to obtain
Employment law obligations in the target jurisdiction that the acquirer didn't model in their financial projections
Regulatory approvals required in Canada (Competition Act) that weren't anticipated in the deal timeline
None of these are surprises if you have the right counsel. All of them are expensive surprises if you don't.
The fix: On any cross-border M&A transaction, both sides need counsel that understands both sides. The transaction structure needs to be designed from the beginning to work in both jurisdictions. Retrofitting is expensive.
The pattern underneath all of this
The common thread in all of these mistakes is the same: founders assume similarity where there is difference, and assume difference where there is similarity.
Canada and the United States share a language, a border, and a lot of cultural overlap. The legal systems share common law roots. It's natural to assume the frameworks are more similar than they are.
They're not. The differences are specific, they matter, and they show up at the worst possible moments — in the middle of a deal, in the middle of a dispute, in the middle of a due diligence process that was supposed to close last week.
Cross-border legal strategy is not a specialty add-on. If you operate in both countries, it's the baseline. The question isn't whether you need it — it's whether you have it before something goes wrong, or after.
If you're building in both markets and want to talk through where the gaps might be, book a 30-minute call →
— Kristina Kang, Rebel Sage Legal New York · Ontario · rebelsagelegal.com
